It could have been better if the odm related compose are in the seperate compose file like docker-compose.odm.yml. So, If I don't want odm in my setup, I wouldn't have it in my setup.

Yeah for sure I can do that 👍

Done.

Now to run only ODM:

docker compose -f docker-compose.odm.yml up -d

or to run it alongside Drone TM:

docker compose -f docker-compose.yml -f docker-compose.odm.yml up -d

Although in my opinion, these should be merged back together in future, as we use the main docker-compose.yml only for local development & it makes sense to bundle ODM there (or at minimum a single NodeODM instance).

The docker-compose.vm.yml is used to deploy to prod for now, so is not affected.

Yes, you are right. But, we could use the above command too.
Another question is, how does web odm stores volumes. Does it support minio ? We might want to store images, orthos, everything in s3.

I commented on the discussion here about this topic: #94

Probably best we have a call at some point to discuss this.

For the POC using locally hosted Minio (essentially storing all images on-disk with an S3 wrapper) is probably ok, but we need large storage attached to the machine we deploy to.

S3 is still the way to go in the future, but probably an externally hosted one. ODM does not support bulk file import from S3 though. To import in bulk via the NodeODM API we would need to zip the files first